Explicitly label .origin files as configuration
authorColin Walters <walters@verbum.org>
Thu, 22 Jan 2015 22:35:32 +0000 (17:35 -0500)
committerColin Walters <walters@verbum.org>
Fri, 23 Jan 2015 17:44:06 +0000 (12:44 -0500)
commit6ce80f9685e6273dbcb4731d6650a10976ea220a
treea21d00fa425b6648925380207786014ae12a0c34
parent8f4999c854f066c11f5137771697c79928044e5d
Explicitly label .origin files as configuration

subscription-manager has a daemon that runs in a confined domain,
and it doesn't have permission to write usr_t, which is the default
label of /ostree/deploy/$osname/deploy.

A better long term fix is probably to move the origin file into the
deployment root as /etc/ostree/origin.conf or so.

In the meantime, let's ensure the .origin files are labeled as
configuration.
src/libostree/ostree-sepolicy.c
src/libostree/ostree-sepolicy.h
src/libostree/ostree-sysroot-deploy.c
src/libostree/ostree-sysroot-private.h
src/libostree/ostree-sysroot.c